Reports Reporting Entities Reporting Entities view Reporting Entity form Configured Fields tab or from the online help.Use this setting to load an XML file that maps additional fields for the billing extract. You can use the XML file to map additional fields, such as appointment related fields that are not already included in the Chargeable Appointment Events view (on page 1) or any flex fields, to be extracted as part of a billing extract. These fields may be flex fields configured for the entity or additional built-in fields that are not a part of the extract, by default. These fields are included with the rest of the N4 fields when you run the billing extract for the appointment events recorded for your site.
You can use the mapping file to map additional fields, String, Date, Long and Double data types. When configuring the mapping file, the field name specified in the value attribute must exactly match the External Tag specified for the field in the corresponding reporting entity. If it is not a valid map, N4 does not extract the field.
The External Tag is case-sensitive and must match exactly as listed in the corresponding reporting entity. You can view the External Tag either from the Configuration Reports Reporting Entities Reporting Entities view Reporting Entity form Configured Fields tab or from the online help.
For more information on the format of the file, see Appointment billing extract mapping file (on page 1) in the online help or on the Kaleris Community Portal. After you load the billing extract mapping file, N4 includes these additional fields in the billing extract.
In the Chargeable Appointment Events view, N4 does not display the mapped field name as the column heading; instead, it displays the Label for the billing flex field as the column heading. For example, you may map the ApptNotes field in N4 to the bexaFlexString01 flex field. In the Chargeable Appointment Events view, N4 displays Flex String 01 as the column heading instead of ApptNotes.